Release 10.1A: OpenEdge Development:
Progress Dynamics Administration

How Progress Dynamics uses profile data in a session

The Profile Manager provides the program interface for profile data between the Repository and your application. It provides you with the option to store selected profile data for the duration of a single session or permanently between sessions, which you can have an application user decide. The Profile Manager stores values, by user, for each affected profile code in the Repository. At initial application startup, a default value is used for each setting until the user performs an application function that changes the value, such as changing the size of a window. You can also provide options that let the user decide whether certain profile types and codes affect application behavior.

For an example of user profile data in an application, review the Preferences function that is, by default, built into the Administration and Development windows. You can see how it works for the user by changing these settings in the Administration tool or the Development tool. You can provide additional user profile options in your own applications by defining the profile types and codes, as described in this section, and by referencing and updating their values at run time using the Profile Manager API.

Note: User profiles are not directly linked to Progress Dynamics security. Instead, Progress Dynamics uses a group-based security model. For more information on how to set up security in Progress Dynamics, see Chapter 3, " Setting Up Basic Security Options."